<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>DocFlex/XML (Kit), Version 1.6.7 - Release Notes</title></head>

<style type="text/css">

body {
  font-family:Arial, Helvetica, sans-serif;
}

code {
  white-space:nowrap;
}

.note {
  font-size:90%;
  padding: 4px;
  border: solid 1px #999999;
  background-color:#EEEEEE;
}

.mrg0 {
  margin-top:0pt;
  margin-bottom:0pt;
}

</style>

<body>

<center>
  <h1>DocFlex/XML (Kit), Version 1.6.7</h1>
  <h2>Release Notes</h2>
</center>

<hr>

<h2>Table Of Contents</h2>
<ul>
  <li><a href="#about">About Freeware Edition</a></li>
  <li><a href="#contents">Package Contents</a></li>
  <li><a href="#requirements">Technical Requirements</a></li>
  <li><a href="#installation">Installation</a>
    <ul>
      <li><a href="#windows_installation">Windows Installation</a></li>
      <li><a href="#linux_installation">Linux Installation</a></li>
    </ul>
  </li>
  <li><a href="#running_xmldoc">Running XMLDoc</a></li>
  <li><a href="#running_xsddoc">Running XSDDoc</a></li>
  <li><a href="#getting_help">Getting Help</a></li>
  <li><a href="#change_log">Change Log</a></li>
</ul>

<hr>

<h2>
  <a name="about"></a>
  About Freeware Edition
</h2>

DocFlex/XML (Kit) is a freeware edition of 
<a href="http://www.filigris.com/products/docflex_xml/" target="_blank">DocFlex/XML</a>
supposed for the following purposes:
<ul>
  <li>
    <p>As a freeware documentation generator for several standard XML applications
    using basic templates included in the packages:</p>
    <ol>
      <li>
        <p><a href="#running_xmldoc"><b>XMLDoc</b></a> (<i>"XML File Documentor"</i>)
        set of templates will allow you to compile any number 
        of generic XML files into a nice looking web-ready HTML or printable 
        RTF documentation with the optional inclusion of a namespace binding report.</p>
      </li>
      <li>
        <p><a href="#running_xsddoc"><b>XSDDoc</b></a> (<i>"XML Schema Documentation Generator"</i>)
        set of templates implements a professional quality documentation generator for any W3C XML Schema
        able to produce both multi-framed Javadoc-like HTML and printable RTF documentation.</p>
      </li>
    </ol>
  </li>
  <li>
    As a command line interpreter for your custom templates -- 
    only those created with the licensed full version!
  </li>
</ul>

Limitation of freeware edition:
<ul>
  <li>
    The freeware edition has no specific limitations on the size or content of the processed XML (or XSD) files.
    It is up to the particular templates and the whole technology as is what you can do with it!
    <p>
  </li>
  <li>
    The Template Designer is not included in the freeware edition. 
    You can neither create new templates nor modify the existing ones.
  </li>
</ul>

<h2>
  <a name="contents"></a>
  Package Contents
</h2>

<table cellspacing="1" cellpadding="5" border="1">

<tr valign="top">
  <td>
    <code>LICENSE.html</code>
  </td>
  <td>
    <a href="LICENSE.html">DocFlex Freeware Edition License</a>
  </td>
</tr>

<tr valign="top">
  <td>
    <code>README.html</code>
  </td>
  <td>
    this file
  </td>
</tr>

<tr valign="top">
  <td>
    <code>doc/</code>
  </td>
  <td>
    <a href="doc/index.html">documentation</a>
  </td>
</tr>

<tr valign="top">
  <td>
    <code>generator.bat</code>
  </td>
  <td>
    starts DocFlex/XML generator
  </td>
</tr>

<tr valign="top">
  <td><code>
    linux/<br>
    linux/generator.sh<br>
    linux/docflex.config</code>
  </td>
  <td>
    contains files used for <a href="#linux_installation">Linux Installation</a>:
    <ul class="mrg0">
      <li>shell script file to start DocFlex/XML generator
      <li>the main DocFlex config file prepared for Linux installation
    </ul>
  </td>
</tr>

<tr valign="top">
  <td><code>
    config/<br>
    config/xmltypes.config<br>
    config/generator.config</code>
  </td>
  <td>
    Configuration&nbsp;files:
    <ul class="mrg0">
      <li>XML Types config file (prepared to run basic templates and samples)
      <li>The Generator config file
    </ul>
  </td>
</tr>

<tr valign="top">
  <td><code>
    lib/<br>
    lib/docflex-xml-kit.jar<br>
    lib/docflex.config<br>
    lib/xml-apis.jar<br>
    lib/xercesImpl.jar</code>
  </td>
  <td>
    Runtime Environment:
    <ul class="mrg0">
      <li>DocFlex/XML Java library</li>
      <li>
        The main config file (contains locations of other config files
        and various important settings)
      </li>
      <li><a href="http://xml.apache.org/xerces2-j/" target="_blank">Apache Xerces2 Java Parser</a></li>
    </ul>
  </td>
</tr>

<tr valign="top">
  <td>
    <code>lib/xsd/</code>
  </td>
  <td>
    contains XML schema for W3C XML Schemas, which is used by <a href="#running_xsddoc">XSDDoc</a> 
    templates simultaneously for two purposes:
    <ol class="mrg0">
      <li>For their internal working (XSDDoc templates are just constructed basing on that schema)</li>
      <li>For <a href="#running_xsddoc">running</a> a demo generation of an XML schema documentation</li>
    </ol>
  </td>
</tr>

<tr valign="top">
  <td><code>
    templates/<br>
    templates/XMLDoc.tpl<br>
    templates/XMLDocFrames.tpl<br>
    templates/xmldoc/<br>
    templates/XSDDoc.tpl<br>
    templates/XSDDocFrames.tpl<br>
    templates/xsddoc/</code>
  </td>
  <td>
    Basic templates:
    <ul>
      <li><i>"XML File Documentor"</i> (<a href="#running_xmldoc">XMLDoc</a>) template set</li>
      <li><i>"XML Schema Documentation Generator"</i> (<a href="#running_xsddoc">XSDDoc</a>) template set</li>
    </ul>
  </td>
</tr>

<tr valign="top">
  <td>
    <code>examples/HumanEvolution.xsd</code>
  </td>
  <td>
    A demo XML schema that shows in every detail how to use XHTML and insert images
    in XML schema annotations.
    Run with both <code>templates/XSDDocFrames.tpl</code> (HTML output)
    and <code>templates/XSDDoc.tpl</code> (RTF output).
    This will look fun!
  </td>
</tr>

</table>

<h2>
  <a name="requirements"></a>
  Technical Requirements
</h2>

DocFlex/XML (Kit) requires
Java<sup><font size=-2>TM</font></sup> 2 Runtime Environment (JDK or JRE) 
version 6.x, 5.x or 1.4.x installed on your system.
<p>
You can freely download Java from Sun Java Technology web-site:
<a href="http://java.sun.com/" target="_blank">http://java.sun.com</a>
<p>
To parse XML files, DTDs and XML Schemas, DocFlex/XML uses 
<a href="http://xml.apache.org/xerces2-j/" target="_blank">Apache Xerces2 Java Parser</a> version 2.9.0.
In the case of any questions concerning this library, please refer to the Apache Xerces home page:
<a href="http://xerces.apache.org" target="_blank">http://xerces.apache.org</a>.
<p>
To generate XML schema documentation (for big and middle sized XML schemas) using 
<a href="#running_xsddoc">XSDDoc</a> template set, you may need a powerful enough computer 
(e.g. with Intel Pentium 4 or AMD Athlon processor) and at least 512 MB RAM memory.

<h2>
  <a name="installation"></a>
  Installation
</h2>

<h3>
  <a name="windows_installation"></a>
  Windows Installation
</h3>

To install DocFlex/XML (Kit) on Windows, please follow these steps:

<ol>
  <li>
    Unpack the downloaded archive.
  </li>
  <li>
    Edit <b><code>generator.bat</code></b> to specify the <b><code>'JRE'</code></b>
    variable according to the location of Java 5 or Java 1.4.x installed on your system.
  </li>
</ol>

Now, you can start <code>generator.bat</code> to launch DocFlex/XML Generator
and run basic templates.

<h3>
  <a name="linux_installation"></a>
  Linux Installation
</h3>

To install DocFlex/XML (Kit) on Linux, please follow these steps:

<ol>
  <li><p>Unpack the downloaded archive.</p>

  <li><p>Copy <code><b>linux/generator.sh</b></code> shell script file to DocFlex/XML Kit 
  root directory and edit it to specify the <code><b>'JRE'</b></code> variable according to 
  the location of Java 5 or Java 1.4.x installed on your system.</p>

  <p>Edit "Permission" properties of <code><b>generator.sh</b></code> file 
  to allow it being executed by Linux.</p>

  <li><p>Copy <code><b>linux/docflex.config</b></code> file to <code><b>lib</b></code> directory.

  <p>Specifically, this file contains settings prepared for Linux to launch automatically 
  a viewer for generated documentation. In particular, those settings specify that 
  each RTF document should be open with OpenOffice.org Writer and each HTML -- with
  Firefox web browser. If you need to use different applications for opening those files,
  please edit <code>docflex.config</code> according to the instruction contained in it.</p>
</ol>

Now, everything must be ready. Just run <code>generator.sh</code>!

<h2>
  <a name="running_xmldoc"></a>
  Running XMLDoc
</h2>

To generate XML File documentation in RTF output format, please do the following:

<ol>
  <li>
    Run <b><code>generator.bat</code></b>. You will see the generator dialog.
  </li>
  <li>
    In "Template" field, select <b><code>XMLDoc.tpl</code></b> template.
  </li>
  <li>
    In "XML File(s)" field, specify one or many XML files that you want to document.</p>
    <p class="note">
      Each XML file can be specified either by local path name or by URL.
      In the case of a URL, the generator will try to download such a file directly from the Internet.
      When multiple XML files are specified, make sure that each pathname or URL is enclosed in double quotes.
    </p>
  </li>
  <li>
    In "Output format" field, select <b>RTF</b> format.
  </li>
  <li>
    Click &lt;Run&gt; button to start generator.
  </li>
</ol>

<h2>
  <a name="running_xsddoc"></a>
  Running XSDDoc
</h2>

To generate XML Schema documentation, please follow these steps:

<ol>
  <li>
    <p>Run <b><code>generator.bat</code></b>. You will see the generator dialog.</p>

    <p class="note">
      While processing XSDDoc templates for big XML Schemas, the generator may be particularly 
      hungry for memory. Lack of memory may considerably increase the generation time! 
      To avoid this, make sure the maximum heap size available for JVM is 512Mb or even more 
      (e.g. Java option <code>-Xmx512m</code> sets the maximum heap size to 512Mb).
    </p>
  </li>
  <li>
    <p>In <b>"Template"</b> field, select <b><code>XSDDocFrames.tpl</code></b> template.</p>

    <p class="note">
      You can choose this template from <code>'templates'</code> directory using File Chooser.
    </p>
  </li>
  <li>
    <p>In <b>"XML File(s)"</b> field, specify one or many XSD files from which you want to generate
    the XML schema documentation.</p>

    <p class="note">
      Each XML file can be specified either by local path name or by URL 
      (e.g. <code>http://www.w3.org/2001/XMLSchema.xsd</code>). 
      In the case of a URL, the generator will try to download such a file directly from the Internet.
      <br><br>
      When multiple XML files are specified, make sure that each pathname or URL is enclosed in double quotes.
    </p>
  </li>
  <li>
    <p>In <b>"Output format"</b> field, select <b>HTML</b> format.</p>

    <p class="note">
      The <code>XSDDocFrames.tpl</code> template is a frameset template 
      which can generate only HTML output!
    </p>
  </li>
  <li>
    <p>Click <b>"Run"</b> button to start generator.</p>

    <p class="note">
      Once all source XML Schema files are loaded, the generator enters into the <b><i>estimation phase</i></b>.
      Lots of heavy processing is being done during that, however, you will see only 
      <i>"Scanning data source, please wait..."</i> message on the progress bar.
      On large XML schemas this phase may take some time. Please wait!
      After that, the generator will pass into the <b><i>generation phase</i></b>.
      The progress bar will show what's being generated.
      <br><br>
      You can stop the generator at any time during any phase by clicking <b>"Cancel"</b> button.
    </p>
  </li>
</ol>

<h2>
  <a name="getting_help"></a>
  Getting Help
</h2>

We are happy to hear any questions, suggestions, comments, etc.
about this product.
<br>
Please, e-mail us to: <a href="mailto:support@docflex.com">support@docflex.com</a>
<p>
Check the latest releases and documentation updates at:
<a href="http://www.filigris.com" target="_blank">www.filigris.com</a>.

<h2>
  <a name="change_log"></a>
  Change Log
</h2>

<i>This is the change log of the entire 
<a href="http://www.filigris.com/products/docflex_xml/" target="_blank">DocFlex/XML</a> product.
The freeware edition "DocFlex/XML (Kit)" is mentioned here as a part of the whole thing.</i>

<h3>
  Version 1.6.7
</h3>

<ul>

<li><b>Improvements of "<a href="#running_xsddoc">XSDDoc</a>" templates</b>
<p>
<ul>
  <li>
    Fixed repeated documenting of the same schemas which were both specified on the 
    generator command line and loaded from other schemas with one of the <code>&lt;xs:import&gt;</code>,
    <code>&lt;xs:include&gt;</code>, <code>&lt;xs:redefine&gt;</code> directives.
    <p>
  </li>
  <li>
    In the <i>"Usage / Definition Locations"</i> section of component documentation, 
    now the links (page numbers) are generated to the local details about that component 
    (within other component where it is used/defined).
    <p>
  </li>
</ul>
<p>
</li>

<li><b>Template interpreter / output generator</b>
<p>
<ul>
  <li>
    A bug has been fixed which caused <code>java.lang.ClassCastException</code> exception
    happening when a schema with unspecified (i.e. global) target namespace imported another schema using
    <code>&lt;xs:include&gt;</code> directive.
    <p>
  </li>
  <li>
    Reworked scaling of images in HTML.
    <p>
    In templates, the new image size must be specified in device-independent units (like points).
    Before that, it was an HTML browser who converted points into pixels, which might be
    responsible for producing images with unpredictable sizes.
    <p>
    Now, when generating HTML, the DocFlex generator itself converts point size into pixel size according 
    to the DPI value specified in the formatting properties of the given templates
    (see: <i>Template Designer | File | Properties | Formatting | General | Resolution (DPI)</i>).
    So, in HTML, the new image size will always be specified in pixels.
    <p>
  </li>
  <li>
    Support of images in BMP format.
    <p>
    Now, all supported image formats include: GIF, PNG, JPG, WMF, BMP
  </ul>
</ul>
</li>

</ul>

<h3>
  Version 1.6.6
</h3>

<dl>
<dd>
  Upgrade with the latest DocFlex core optimized for Java 6
</dd>
</dl>

<h3>
  Version 1.6.5
</h3>

<ul>

<li><b>Upgrade with the latest Apache Xerces2 Java Parser 2.9.0</b>
<p>
This open source Java library is used by DocFlex/XML (all editions) and 
included in the package (see <a href="#contents">Package Contents</a>).
Support of the newest version of <a href="http://xerces.apache.org" target="_blank">Apache Xerces</a>
will help to integrate DocFlex/XML seamlessly with the latest versions of other 
important tools (e.g. <a href="http://ant.apache.org" target="_blank">Apache Ant</a>).
<p>
</li>

<li><b>Fixing a bug</b>
<p>
The bug happened when DocFlex/XML home directory was placed inside another directory 
whose name contained a space (e.g. <code>'C:\Program Files\docflex-xml-kit'</code>).
It caused <code>java.io.FileNotFoundException</code> during opening the configuration files. 
Now, this is working.
</li>

</ul>

<h3>
  Version 1.6.4
</h3>

<dl>
<dd>
  Additions/improvements of the documentation.
</dd>
</dl>

<h3>
  Version 1.6.3
</h3>

<ul>

<li><b>Template interpreter / output generator</b>
<p>
<ul>
  <li>
    The general performance has been improved (about 5%).
    <p>
  </li>
  <li>
    Better support for image formatting. 
    Now, an image can be aligned both to the left or right of a text and wrapped by it.
    This is supported both in HTML and RTF output.
    An image can be aligned directly in a template (e.g. by specifying properties of an Image Control) 
    or using <b><code>align</code></b> attribute of an <b><code>&lt;img&gt;</code></b> tag in 
    a description preformatted with HTML/XHTML markup.
  </li>
</ul>
<p>
</li>

<li><b>Template language / Generator Object Model (GOM)</b>
<p>
<ul>
  <li>
    <i>Init/Finish Expressions</i> are now supported in Area Sections.
    <p>
  </li>
  <li>
    The font size assigned to a particular template component can be specified now
    not only as a fixed value but also relatively (in percents) to the font size
    of component's context. 
    (See component's Properties Dialog | Formatting | Text tab).
    <p>
  </li>
  <li>
    The "Alignment" formatting property of Image Control has been extended up to five
    possible setting: 
    <p>
    <ol>
      <li><i>Bottom (base line)</i></li>
      <li><i>Middle (base line)</i></li>
      <li><i>Top (text line)</i></li>
      <li><i>Left (margin)</i></li>
      <li><i>Right (margin)</i></li>
    </ol>
    <p>
    (See Image Control Properties Dialog | Formatting | Image tab).
    <p>
  </li>
  <li>
    The <b><code>firstSentence()</code></b> function, which extracts the first sentence
    from a long description text to be placed in a summary table, has been totally redeveloped.
    Now, it recognizes the HTML markup and finds the first sentence boundary according 
    to the pure text extracted from the original string (i.e. without HTML tags) as well as
    stops on any HTML block tag (such as &lt;p&gt;). In the returned string, the original HTML 
    markup is preserved and unfinished HTML elements are correctly closed.
    (See Template Designer | <i>Help | Expression Assistant</i> dialog for more info).
    <p>
  </li>
  <li>
    A new GOM property <b><code>OutputFormat.renderEmbeddedHTML</code></b> has been added
    to indicate if <i>"Render embedded HTML"</i> format option has been specified for the generator.
    Now, this property is used in XSDDoc templates to better control processing of XHTML in 
    XML schema annotations.
  </li>
</ul>
<p>
</li>

<li><b>"<a href="#running_xsddoc">XSDDoc</a>" templates (The XML Schema documentation generator)</b>
<p>
<ul>
  <li>
    A bug has been fixed. There was a wrong query in <code>xsddoc/init.tpl</code> template, 
    which caused the attributes specified within a child element defined locally within 
    another element to be documented also as the attributes of the parent element.
    <p>
  </li>
  <li>
    Each reproduced XML source fragment (e.g. the definition of a component) 
    now is hyperlinked to the location of that fragment within the reproduced full 
    XML schema source. The link is placed in the "XML Source" heading.
    <p>
  </li>
  <li>
    Since XHTML formatting in annotations may occupy a lot of space in the reproduced XML source, 
    it may just overwhelm anything else. So, now, a group of parameters has been introduced in
    <code>XSDDoc.tpl</code> and <code>XSDDocFrames.tpl</code> templates to remove 
    <code>&lt;xs:annotation&gt;</code> elements from the reproduced XML source
    (see in parameter inspector <i>"Sections | XML Source | Remove Annotation"</i>).
    This can by controlled specifically for different types of XML source fragments 
    (e.g. for components the annotation can be removed, but the full XML schema source 
    will be reproduced as is).
    <p>
  </li>
  <li>
    The XHTML markup specified in XML schema annotations is now also reproduced in 
    the brief descriptions (first sentences) placed in summary tables (e.g. Element Summary).
    <p>
  </li>
  <li>
    A new template parameter <i>"Include images"</i> (see <i>"Sections | Annotation | Include images"</i>
    in the parameter inspector dialog) has been added to control whether to include images specified 
    (with the XHTML <code>&lt;img&gt;</code> tags) in XML schema annotations.
    <p>
  </li>
</ul>
<p>
</li>

</ul>

<h3>
  Version 1.6.2
</h3>

<ul>

<li><b>Template interpreter / output generator</b>
<p>
<ul>
  <li>
    Now, the generator consumes considerably less memory and works up to 10% faster!
  </li>
  <li>
    The error reporting, when the generator works without GUI, is directed now to the 
    <code>stderr</code> (by default) or in a separate <code>'docflex_error.log'</code> file 
    (when it is specified with the newly introduced <b><code>-errlog</code></b> option).
  </li>
</ul>
<p>
</li>

<li><b>Generator Object Model (GOM)</b>
<p>
<ul>
  <li>
    New properties
    <b><code>GOMIterator.prevItem</code></b> and <b><code>GOMIterator.nextItem</code></b>
    were introduced as well as a method accompanying them: 
    <b><code>GOMIterator.itemAt()</code></b>.
    <p>
  </li>
  <li>
    More new properties: <b><code>DSMElement.rawValue</code></b> and 
    <b><code>DSMAttr.rawValue</code></b>. These properties allow to access the unprocessed 
    text values of XML elements/attributes directly obtained from the XML files. 
    You can use this, for instance, like the following:
    <b><code>contextElement.dsmElement.rawValue</code></b> 
    (e.g. in the Formula Expression of a Data Control).
  </li>
</ul>
<p>
For details, see Template Designer | <i>Help | Expression Assistant</i> dialog.
</li>
</ul>

<h3>
  Version 1.6
</h3>

<ul>
<li>
  <b>New documentation</b>
  <p>
  All generator properties accessible within FlexQuery expressions (&gt; 100) as well as
  all general (148) and XML-specific (18) FlexQuery functions are fully documented now.
  In total this took writing more than 330 KB of explanations in HTML!
  <p>
  You can find everything at the Template Designer | Help | Assistant dialog.
  <p>
</li>
<li>
  <b>Support of XHTML tags within XML Schema annotations</b>
  <p>
  The "<a href="#running_xsddoc">XSDDoc</a>" templates are upgraded now to support 
  the XML Schema annotations (the content of <code>&lt;xs:annotation&gt;</code> elements) 
  preformatted with XHTML tags, including possibility to insert images 
  (using <code>&lt;xhtml:img&gt;</code> tag).
  <p>
  The processing of XHTML tags is programmed entirely within <code>annotation.tpl</code> 
  subtemplate (located at <code>templates/xsddoc/misc/</code> directory). 
  All XHTML tags are converted to the normal HTML tags (actually, just 
  <code>'xhtml'</code> namespace prefix is removed from the tag names).
  Further, everything is processed by the generator itself.
  <p>
  In the case of <b>HTML output</b>, each annotation text together with HTML tags is inserted
  as is into the generated output file. Additionally, the image files specified in 
  <code>&lt;xhtml:img&gt;</code> tags can be copied automatically to the documentation 
  destination directory. This is also programmed in <code>annotation.tpl</code> subtemplate
  and controlled by <i>"Formatting | Annotation | Copy images"</i> parameter of both
  <code>XSDDoc.tpl</code> and <code>XSDDocFrames.tpl</code> main templates.
  <p>
  In the case of <b>RTF output</b> (generated with <code>XSDDoc.tpl</code> template), 
  all HTML tags embedded in annotations are parsed and interpreted with the appropriate 
  RTF formatting features. Almost all HTML tags (and their attributes) practically 
  usable in documentation comments are processed in that way. Here's the list 
  of all supported HTML tags:
  <p>
  <table border="1" cellspacing="1" cellpadding="5">
  <tr valign="top">
    <td><b>Text</b></td>
    <td>
      &lt;b&gt;, &lt;strong&gt;, &lt;i&gt;, &lt;em&gt;, &lt;code&gt;, &lt;tt&gt;, &lt;u&gt;,
      &lt;s&gt;, &lt;strike&gt;, &lt;sub&gt;, &lt;sup&gt;, &lt;font&gt;, &lt;br&gt;
    </td>
  </tr>
  <tr valign="top">
    <td><b>Paragraphs</b></td>
    <td>
      &lt;p&gt;, &lt;center&gt;, &lt;div&gt;, &lt;pre&gt;, &lt;h1&gt;, &lt;h2&gt;, &lt;h3&gt;,
      &lt;h4&gt;, &lt;h5&gt;, &lt;h6&gt;, &lt;blockquote&gt;
    </td>
  </tr>
  <tr valign="top">
    <td><b>Lists</b></td>
    <td>
      &lt;ul&gt;, &lt;ol&gt;, &lt;li&gt;, &lt;dl&gt;, &lt;dt&gt;, &lt;dd&gt;
    </td>
  </tr>
  <tr valign="top">
    <td><b>Table</b></td>
    <td>
      &lt;table&gt;, &lt;tr&gt;, &lt;td&gt;, &lt;th&gt;
    </td>
  </tr>
  <tr valign="top">
    <td><b>Other</b></td>
    <td>
      &lt;hr&gt;, &lt;img&gt;, &lt;a&gt;...&lt;/a&gt;
    </td>
  </tr>
</table>
</li>
</ul>

<h3>
  Version 1.5
</h3>

<dl>
<dd>
  <b>The major breakthrough!</b>
  <p>
  <ul>
    <li>
      Now, DocFlex/XML supports processing with the same template any number of XML files at once 
      (based on the same DTD or XML scheme), which are represented as a single meta-XML document.
      <p>
    </li>
    <li>
      The data querying capabilities are enormously enhanced by introducing <i>Element Maps</i>
      and <i>formula-axis</i> in Location Paths / Location Rules.
      Lots of new embedded FlexQuery functions have been added.
      <p>
    </li>
    <li>
      The first real-world and very powerful template application has been developed
      basing on this new functionality -- the "<a href="#running_xsddoc">XSDDoc</a>" 
      set of templates that implements a superior quality XML schema documentation generator!
      <p>
    </li>
    <li>
      The freeware edition of DocFlex/XML called <i>"DocFlex/XML (Kit)"</i> has been released,
      which basically includes the template interpreter/documentation generator without the
      Template Designer. The freeware edition can be used as a runtime environment for executing 
      your custom templates. In addition, it includes "<a href="#running_xsddoc">XSDDoc</a>" 
      and "<a href="#running_xmldoc">XMLDoc</a>" sets of templates that allow using it 
      simply as the best quality documentation generator for your XML Schemas or raw XML files 
      available absolutely for free!
      <p>
    </li> 
  </ul>
</dd>
</dl>

<h3>
  Version 1.0
</h3>

<dl>
<dd>
  <b>Here, the story begins!</b>
  <p>
  The first version DocFlex/XML has been released, which started the third and the most advanced product line
  based on <a href="http://www.filigris.com/products/docflex/" target="_blank">DocFlex Technology</a>.
  (The previous two,
  <a href="http://www.filigris.com/products/docflex_javadoc/about.php" target="_blank">DocFlex/Javadoc</a> and 
  <a href="http://www.filigris.com/products/docflex_together/about.php"target="_blank">DocFlex/Together</a>,
  had been already available for more than a year before that.)
  <p>
  Most of the document formatting capabilities was already in place. 
  All processing of XML files was already based on the data type information obtained from DTD or XML Schemas.
  However, the actual data sources possible to process at once with a single template were limited to only
  one XML file.
  <p>
  The <i>"Sales Report"</i> and <i>"Alternative to XSLT"</i> <a href="#running_samples">samples</a> 
  are coming from those times.
</dd>
</dl>

<hr>
<span style="font-family: Verdana, helvetica;font-size: 13px;">
Copyright&copy; 2007 Filigris Works, Leonid Rudy Softwareprodukte. All rights reserved.<br>
To contact us, please visit
<a href="http://www.filigris.com" target="_blank">www.filigris.com</a> or
e-mail to: <a href="mailto:contact@filigris.com">contact@filigris.com</a>
</span>

</body>
</html>
